Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1adee7629dd2123570acdc3a06fd07fd2ccbe377bdd7423773f6276be0f41bc

Tx prefix hash: 3ee505a0b95e8768d26c4d57041a3deecd62c30082a3b4bd16fe6d2bc41e1195
Tx public key: 65d4168c4e54efe1a3183cdefa475b29fda8b801f3c4ac721323bb76d3d7f573
Timestamp: 1720833517 Timestamp [UCT]: 2024-07-13 01:18:37 Age [y:d:h:m:s]: 00:262:05:29:25
Block: 1064478 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187330 RingCT/type: yes/0
Extra: 0165d4168c4e54efe1a3183cdefa475b29fda8b801f3c4ac721323bb76d3d7f57302110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e62f53b82876aeca110092f4f05e79663a19de84b916ec594dade43f60e33d47 0.600000000000 1535005 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": 1064488, "vin": [ { "gen": { "height": 1064478 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e62f53b82876aeca110092f4f05e79663a19de84b916ec594dade43f60e33d47" } } ], "extra": [ 1, 101, 212, 22, 140, 78, 84, 239, 225, 163, 24, 60, 222, 250, 71, 91, 41, 253, 168, 184, 1, 243, 196, 172, 114, 19, 35, 187, 118, 211, 215, 245, 115, 2, 17, 0, 0, 0, 9, 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