Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3d72409a14745a2ac236742529c897de1e7ca491f1f5e4d39875e8bf37b33484

Tx prefix hash: 3ae4606017494889a4cc36e0b01937c1193aa9c393ff1adb6ba9ef29e1f7a3bc
Tx public key: 2617058f0b9e4c77380e2853cad5f54482d69a0b3e880fce1836c34da59a3646
Timestamp: 1732860888 Timestamp [UCT]: 2024-11-29 06:14:48 Age [y:d:h:m:s]: 00:115:17:43:18
Block: 1164078 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 82511 RingCT/type: yes/0
Extra: 012617058f0b9e4c77380e2853cad5f54482d69a0b3e880fce1836c34da59a36460211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 52d351a1ea2e31a3641b0f1a632344d7d94a3ef513749a510ac5c3ccfb103723 0.600000000000 1649751 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": 1164088, "vin": [ { "gen": { "height": 1164078 } } ], "vout": [ { "amount": 600000000, "target": { "key": "52d351a1ea2e31a3641b0f1a632344d7d94a3ef513749a510ac5c3ccfb103723" } } ], "extra": [ 1, 38, 23, 5, 143, 11, 158, 76, 119, 56, 14, 40, 83, 202, 213, 245, 68, 130, 214, 154, 11, 62, 136, 15, 206, 24, 54, 195, 77, 165, 154, 54, 70, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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