Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ad17e45bd08c8b47d92e56444d5c39388b5f55dcf3af0f70252326d466dc0d3d

Tx prefix hash: 3ebc4e9d43462a4f03b8cdbf34d549bcf35e288520205d418e70d25b738a2269
Tx public key: 5e393e7ff960c8a61ab279f2df394e12c7e5e7334ab876d88a8f0bd479c357d4
Timestamp: 1644280418 Timestamp [UCT]: 2022-02-08 00:33:38 Age [y:d:h:m:s]: 02:115:06:17:03
Block: 434144 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 601128 RingCT/type: yes/0
Extra: 015e393e7ff960c8a61ab279f2df394e12c7e5e7334ab876d88a8f0bd479c357d402110000000fa272b9cb000000000000000000

1 output(s) for total of 22.363743901000 dcy

stealth address amount amount idx
00: 3a0ef663960ecaddad73f0154299e04c8f903b8696826d6bf163218451ee10ee 22.363743901000 845029 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": 434154, "vin": [ { "gen": { "height": 434144 } } ], "vout": [ { "amount": 22363743901, "target": { "key": "3a0ef663960ecaddad73f0154299e04c8f903b8696826d6bf163218451ee10ee" } } ], "extra": [ 1, 94, 57, 62, 127, 249, 96, 200, 166, 26, 178, 121, 242, 223, 57, 78, 18, 199, 229, 231, 51, 74, 184, 118, 216, 138, 143, 11, 212, 121, 195, 87, 212, 2, 17, 0, 0, 0, 15, 162, 114, 185, 203, 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