Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6aa57d83f2848d9e9bc3ad10c621fdbaf157cc5e19dd665b10ba0e250f92cc3e

Tx prefix hash: b295708a19c533114f3e7c21c8ab186e8aac0c67408951c4c0146cc983eda2ab
Tx public key: bdc758d48cabc2f89bed35b1b88ff7be7f185e3bbf5801ed91ebcbbf40482d3a
Timestamp: 1702397016 Timestamp [UCT]: 2023-12-12 16:03:36 Age [y:d:h:m:s]: 02:049:13:01:24
Block: 911639 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 555037 RingCT/type: yes/0
Extra: 01bdc758d48cabc2f89bed35b1b88ff7be7f185e3bbf5801ed91ebcbbf40482d3a021100000001faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f1f86e3f7b613f522356abd1f75441d26b6a0f636bfd19e40033243029d24612 0.600000000000 1368853 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": 911649, "vin": [ { "gen": { "height": 911639 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f1f86e3f7b613f522356abd1f75441d26b6a0f636bfd19e40033243029d24612" } } ], "extra": [ 1, 189, 199, 88, 212, 140, 171, 194, 248, 155, 237, 53, 177, 184, 143, 247, 190, 127, 24, 94, 59, 191, 88, 1, 237, 145, 235, 203, 191, 64, 72, 45, 58, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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