Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d6deb816104d2ec5ae703689843779f75dd2631d8909ea9752d081c4c65b5046

Tx prefix hash: f7987f618c71e9bfdaa23361c4944aa2e50a6e2e5dcd4dc44f165be14418a3c4
Tx public key: 8ad72f45fc97289fd191a4d8dadb052474136a76f89574741e077f9efe864e8d
Timestamp: 1726768485 Timestamp [UCT]: 2024-09-19 17:54:45 Age [y:d:h:m:s]: 00:066:07:58:39
Block: 1113667 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 47413 RingCT/type: yes/0
Extra: 018ad72f45fc97289fd191a4d8dadb052474136a76f89574741e077f9efe864e8d021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a9c34f013ed9cbffaf575a104f415193d36f3a4a06591a8e67cba6c46811244 0.600000000000 1593422 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": 1113677, "vin": [ { "gen": { "height": 1113667 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a9c34f013ed9cbffaf575a104f415193d36f3a4a06591a8e67cba6c46811244" } } ], "extra": [ 1, 138, 215, 47, 69, 252, 151, 40, 159, 209, 145, 164, 216, 218, 219, 5, 36, 116, 19, 106, 118, 248, 149, 116, 116, 30, 7, 127, 158, 254, 134, 78, 141, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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