Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 93c1a7f52c897b5c2550b6de3cd5d9bee94bcc66ee48daedcc4ac6c0a35a16ce

Tx prefix hash: 664fac0389d8ff083f85deb5f69d34c1e2f60e9740dd7559e3d519dcdf01c86f
Tx public key: 0e6c951206bca83430e28ccf53515e6d34b78edf0e785a63fba4b50408b871e6
Timestamp: 1681087690 Timestamp [UCT]: 2023-04-10 00:48:10 Age [y:d:h:m:s]: 01:277:19:15:09
Block: 735190 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 460051 RingCT/type: yes/0
Extra: 010e6c951206bca83430e28ccf53515e6d34b78edf0e785a63fba4b50408b871e6021100000002b3164c24000000000000000000

1 output(s) for total of 2.249109308000 dcy

stealth address amount amount idx
00: 4b2f43c11f1ccfa6eecdcb2dfb1ff32b163da77a8bfd127e129a95616a1e17f2 2.249109308000 1181489 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": 735200, "vin": [ { "gen": { "height": 735190 } } ], "vout": [ { "amount": 2249109308, "target": { "key": "4b2f43c11f1ccfa6eecdcb2dfb1ff32b163da77a8bfd127e129a95616a1e17f2" } } ], "extra": [ 1, 14, 108, 149, 18, 6, 188, 168, 52, 48, 226, 140, 207, 83, 81, 94, 109, 52, 183, 142, 223, 14, 120, 90, 99, 251, 164, 181, 4, 8, 184, 113, 230, 2, 17, 0, 0, 0, 2, 179, 22, 76, 36, 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