Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b7735beeac149b87a5ce8d5aee1f7f9f543f85f4f0c52f98baa46fedfd3834b9

Tx prefix hash: 9e92d74899c9e96a5dd7dccfd8a25c6b250e0e28b5d46df340dc9899d83d30a9
Tx public key: 35287c39ab3c7ec7e5dad367d336087ad7081bdb019845e2624118e4d20cc0c7
Timestamp: 1583092384 Timestamp [UCT]: 2020-03-01 19:53:04 Age [y:d:h:m:s]: 05:248:11:40:07
Block: 74962 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1329677 RingCT/type: yes/0
Extra: 0135287c39ab3c7ec7e5dad367d336087ad7081bdb019845e2624118e4d20cc0c70211000000fbc71d3ff9000000000000000000

1 output(s) for total of 346.434051700000 dcy

stealth address amount amount idx
00: 33e928da7fd8977a1cf94c95b6533386aa1cebb417f187d86e55335353e2bfe0 346.434051700000 138576 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": 74972, "vin": [ { "gen": { "height": 74962 } } ], "vout": [ { "amount": 346434051700, "target": { "key": "33e928da7fd8977a1cf94c95b6533386aa1cebb417f187d86e55335353e2bfe0" } } ], "extra": [ 1, 53, 40, 124, 57, 171, 60, 126, 199, 229, 218, 211, 103, 211, 54, 8, 122, 215, 8, 27, 219, 1, 152, 69, 226, 98, 65, 24, 228, 210, 12, 192, 199, 2, 17, 0, 0, 0, 251, 199, 29, 63, 249, 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