Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 3605ccdab2323db3a070c2c1874d07141aaf664c69e2e404b60db20046adccaf

Tx prefix hash: 47b0534262a137b685bb6c83bb4116f0b356724128380bd15cce96779c91f97a
Tx public key: 833d026a6f8bab5aa079b29e503935734edd12fffd1aa23bf2ae8270a2c1d646
Timestamp: 1694383436 Timestamp [UCT]: 2023-09-10 22:03:56 Age [y:d:h:m:s]: 01:206:03:50:10
Block: 845369 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 408428 RingCT/type: yes/0
Extra: 01833d026a6f8bab5aa079b29e503935734edd12fffd1aa23bf2ae8270a2c1d64602110000000475e3f0e9000000000000000000

1 output(s) for total of 0.970379553000 dcy

stealth address amount amount idx
00: eb4bc43d99bd6af3addbfc022332a319d35ae6e2b891c0995ca2be44cb7efb96 0.970379553000 1298747 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 845379, "vin": [ { "gen": { "height": 845369 } } ], "vout": [ { "amount": 970379553, "target": { "key": "eb4bc43d99bd6af3addbfc022332a319d35ae6e2b891c0995ca2be44cb7efb96" } } ], "extra": [ 1, 131, 61, 2, 106, 111, 139, 171, 90, 160, 121, 178, 158, 80, 57, 53, 115, 78, 221, 18, 255, 253, 26, 162, 59, 242, 174, 130, 112, 162, 193, 214, 70, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8