Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2d6e59208f499b37334d63b739adb2d1b96dffa574bd485dced35c6f31e12f7

Tx prefix hash: ee3e2987f40f998e8842bb023e5321922e9276d379cecbc1189c45112324b4d6
Tx public key: f0026af92ebb99f73b0d7a05326bda4bb97efbd52a5e1606e434328222fb8030
Timestamp: 1701075047 Timestamp [UCT]: 2023-11-27 08:50:47 Age [y:d:h:m:s]: 01:050:17:27:54
Block: 900656 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 297636 RingCT/type: yes/0
Extra: 01f0026af92ebb99f73b0d7a05326bda4bb97efbd52a5e1606e434328222fb8030021100000004faf35c9c000000000000000000

1 output(s) for total of 0.636433123000 dcy

stealth address amount amount idx
00: 9f3e50eeb1fb470477410fce9c7103d7d4314f45a1ae882c49023507721b48eb 0.636433123000 1357167 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": 900666, "vin": [ { "gen": { "height": 900656 } } ], "vout": [ { "amount": 636433123, "target": { "key": "9f3e50eeb1fb470477410fce9c7103d7d4314f45a1ae882c49023507721b48eb" } } ], "extra": [ 1, 240, 2, 106, 249, 46, 187, 153, 247, 59, 13, 122, 5, 50, 107, 218, 75, 185, 126, 251, 213, 42, 94, 22, 6, 228, 52, 50, 130, 34, 251, 128, 48, 2, 17, 0, 0, 0, 4, 250, 243, 92, 156, 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