Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1137f6798cc94f9e1fc7f324b6d958fe51a867e4051b54c424cb09ec93f02fa8

Tx prefix hash: e660293fb77805c377a8a99a1f98c6b84b11d4fb4b1553659e698665de012bb4
Tx public key: 0355f738968371f8f2cf86a332c10912e1aa133a08af0bb299cc8dab54f63f27
Timestamp: 1581252713 Timestamp [UCT]: 2020-02-09 12:51:53 Age [y:d:h:m:s]: 04:291:21:41:54
Block: 61400 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1100657 RingCT/type: yes/0
Extra: 010355f738968371f8f2cf86a332c10912e1aa133a08af0bb299cc8dab54f63f270211000000148a2ee0d9000000000000000000

1 output(s) for total of 384.206434231000 dcy

stealth address amount amount idx
00: 63902569658486e3efb72e15d1e35009272e7ed0e79e29ebfd5fe319fb650328 384.206434231000 113147 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": 61410, "vin": [ { "gen": { "height": 61400 } } ], "vout": [ { "amount": 384206434231, "target": { "key": "63902569658486e3efb72e15d1e35009272e7ed0e79e29ebfd5fe319fb650328" } } ], "extra": [ 1, 3, 85, 247, 56, 150, 131, 113, 248, 242, 207, 134, 163, 50, 193, 9, 18, 225, 170, 19, 58, 8, 175, 11, 178, 153, 204, 141, 171, 84, 246, 63, 39, 2, 17, 0, 0, 0, 20, 138, 46, 224, 217, 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