Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ca33453663d6d0f1a97ab62f87f2afb4c6c29228df4d018625e68f11ee15381d

Tx prefix hash: 5df7916ded37021a7026f89017ff96537b47ce7ca6153458a24307c54befd1ef
Tx public key: 8be2eacd20cf721ecfad3fb6b956c90014e380d4386a5f3c76a276bebd766dd9
Timestamp: 1675606074 Timestamp [UCT]: 2023-02-05 14:07:54 Age [y:d:h:m:s]: 01:345:07:09:49
Block: 690395 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 507746 RingCT/type: yes/0
Extra: 018be2eacd20cf721ecfad3fb6b956c90014e380d4386a5f3c76a276bebd766dd90211000000015029cbac000000000000000000

1 output(s) for total of 3.165444444000 dcy

stealth address amount amount idx
00: 38c4c51d98aa0795224c24c596bfaf574f45704a3662b0d9d0abcfbc854f3f2e 3.165444444000 1133123 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": 690405, "vin": [ { "gen": { "height": 690395 } } ], "vout": [ { "amount": 3165444444, "target": { "key": "38c4c51d98aa0795224c24c596bfaf574f45704a3662b0d9d0abcfbc854f3f2e" } } ], "extra": [ 1, 139, 226, 234, 205, 32, 207, 114, 30, 207, 173, 63, 182, 185, 86, 201, 0, 20, 227, 128, 212, 56, 106, 95, 60, 118, 162, 118, 190, 189, 118, 109, 217, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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