Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ddf3059cfea81fbfa504b4bbedf16e2d21b59930ed0bf9ecb3ee3fb0d0ac393

Tx prefix hash: f15c20770702f1dc3b28178a218a816ed1c39457ff4bd9524ac6909cdc3dce82
Tx public key: 1aa20442983e4b39fc382927ccb07ed2ab5b0e434a3d5021e2fd62f30fb686d1
Timestamp: 1734516389 Timestamp [UCT]: 2024-12-18 10:06:29 Age [y:d:h:m:s]: 00:021:12:04:16
Block: 1177822 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 15347 RingCT/type: yes/0
Extra: 011aa20442983e4b39fc382927ccb07ed2ab5b0e434a3d5021e2fd62f30fb686d10211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5309ee6df0f342380db6028c22ecbd2b85e00439ba8b32dccb7ba8dd4fa08739 0.600000000000 1664199 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": 1177832, "vin": [ { "gen": { "height": 1177822 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5309ee6df0f342380db6028c22ecbd2b85e00439ba8b32dccb7ba8dd4fa08739" } } ], "extra": [ 1, 26, 162, 4, 66, 152, 62, 75, 57, 252, 56, 41, 39, 204, 176, 126, 210, 171, 91, 14, 67, 74, 61, 80, 33, 226, 253, 98, 243, 15, 182, 134, 209, 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