Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4091614c3954ab2b03f19c644d34418c4c8d5b5f15f6bda22df5c916b5df8f33

Tx prefix hash: c2551fb1c55b1320aa772ec547e42b5c3ce90383c3a82a0c3a40cb127280a0ae
Tx public key: 1e9cadcf601c49e4d970415ac31130df6714b78dec3902b3236408edf7e1fe17
Timestamp: 1726060770 Timestamp [UCT]: 2024-09-11 13:19:30 Age [y:d:h:m:s]: 00:074:04:38:42
Block: 1107805 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 53042 RingCT/type: yes/0
Extra: 011e9cadcf601c49e4d970415ac31130df6714b78dec3902b3236408edf7e1fe1702110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 413afe64978ea9a725dcdf0ce3d6cb009d16f0712b585e5d4b333c14a1474df4 0.600000000000 1585476 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": 1107815, "vin": [ { "gen": { "height": 1107805 } } ], "vout": [ { "amount": 600000000, "target": { "key": "413afe64978ea9a725dcdf0ce3d6cb009d16f0712b585e5d4b333c14a1474df4" } } ], "extra": [ 1, 30, 156, 173, 207, 96, 28, 73, 228, 217, 112, 65, 90, 195, 17, 48, 223, 103, 20, 183, 141, 236, 57, 2, 179, 35, 100, 8, 237, 247, 225, 254, 23, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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