Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ed08084f9d7ba181ecd5b62ff18bd2112411dac3fdb75aa40fd97f87112c57fa

Tx prefix hash: f4caf4cdffbb9ebe2abb1a3f7bf83e9fdbc474c5b42138f553c014c10405ab91
Tx public key: cff3c52b901a96fd80be15de1c2ee676e311a37ee841fedf51db26f0366f8e8a
Timestamp: 1733247494 Timestamp [UCT]: 2024-12-03 17:38:14 Age [y:d:h:m:s]: 00:028:22:44:45
Block: 1167284 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 20699 RingCT/type: yes/0
Extra: 01cff3c52b901a96fd80be15de1c2ee676e311a37ee841fedf51db26f0366f8e8a0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4977e2d778c4f9769caa2e9ce5d73d5ad38356ac24ddc5b2ad9943fc1e0d87e6 0.600000000000 1652979 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": 1167294, "vin": [ { "gen": { "height": 1167284 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4977e2d778c4f9769caa2e9ce5d73d5ad38356ac24ddc5b2ad9943fc1e0d87e6" } } ], "extra": [ 1, 207, 243, 197, 43, 144, 26, 150, 253, 128, 190, 21, 222, 28, 46, 230, 118, 227, 17, 163, 126, 232, 65, 254, 223, 81, 219, 38, 240, 54, 111, 142, 138, 2, 17, 0, 0, 0, 5, 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