Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e81909b836b05d00e41569de8f592a99450e7ab0bb0bcb079d36c4cfa72b9bb

Tx prefix hash: 54aacecd1ec0ac770ac6182fab2d4a31ece5a412c7b2a55b6ef024409c970c9f
Tx public key: b70fe8a6537a1515f2f040e6bf36a6bc1911024966219ed3ae053fe3a478a420
Timestamp: 1728970401 Timestamp [UCT]: 2024-10-15 05:33:21 Age [y:d:h:m:s]: 00:039:23:01:28
Block: 1131927 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 28525 RingCT/type: yes/0
Extra: 01b70fe8a6537a1515f2f040e6bf36a6bc1911024966219ed3ae053fe3a478a420021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c9a4e591e38f0b6ce5ff2cdd57b275f4611d0473333db752477c88ca63113617 0.600000000000 1614836 of 15

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": 1131937, "vin": [ { "gen": { "height": 1131927 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c9a4e591e38f0b6ce5ff2cdd57b275f4611d0473333db752477c88ca63113617" } } ], "extra": [ 1, 183, 15, 232, 166, 83, 122, 21, 21, 242, 240, 64, 230, 191, 54, 166, 188, 25, 17, 2, 73, 102, 33, 158, 211, 174, 5, 63, 227, 164, 120, 164, 32, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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