Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d7399e47579a90c2a16ac992eeef7e8b2d3f9dd5f799b2ef9a85e23c80791a14

Tx prefix hash: f45ce2cdf7544697a775cf6cdf393f035ad82a3c0143f48cdc01b95b7ce117a5
Tx public key: 5ab382c8d9a29009e918e0fe3444ffd4c4e7d17745e2bc94597c68ddbfea464a
Timestamp: 1736691900 Timestamp [UCT]: 2025-01-12 14:25:00 Age [y:d:h:m:s]: 00:077:13:07:57
Block: 1195801 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 55189 RingCT/type: yes/0
Extra: 015ab382c8d9a29009e918e0fe3444ffd4c4e7d17745e2bc94597c68ddbfea464a0211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 08c420f0abedb295ef10b5023146286ed021d751a4f8a955abe0f678c641e81e 0.600000000000 1682394 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": 1195811, "vin": [ { "gen": { "height": 1195801 } } ], "vout": [ { "amount": 600000000, "target": { "key": "08c420f0abedb295ef10b5023146286ed021d751a4f8a955abe0f678c641e81e" } } ], "extra": [ 1, 90, 179, 130, 200, 217, 162, 144, 9, 233, 24, 224, 254, 52, 68, 255, 212, 196, 231, 209, 119, 69, 226, 188, 148, 89, 124, 104, 221, 191, 234, 70, 74, 2, 17, 0, 0, 0, 7, 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