Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a281b5d50ed119b0701a1b7b493335adf66ed2902b8efc44e74cb44b01b12425

Tx prefix hash: a413cae39f2e73de066fb990c6cf6b50c6d5356e5ae01b5becc96a757e563b05
Tx public key: ea0d3e1095deb76380c46c1ec522a0695682d019ebef7aacd16beb2d49c02111
Timestamp: 1700891829 Timestamp [UCT]: 2023-11-25 05:57:09 Age [y:d:h:m:s]: 01:140:14:34:38
Block: 899136 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 361668 RingCT/type: yes/0
Extra: 01ea0d3e1095deb76380c46c1ec522a0695682d019ebef7aacd16beb2d49c0211102110000000733af99f4000000000000000000

1 output(s) for total of 0.643856623000 dcy

stealth address amount amount idx
00: 0bc061ddfd3bac5779a0757d4feac373f106fd24bbe159a4b1438ddf42a8fafc 0.643856623000 1355579 of 0

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": 899146, "vin": [ { "gen": { "height": 899136 } } ], "vout": [ { "amount": 643856623, "target": { "key": "0bc061ddfd3bac5779a0757d4feac373f106fd24bbe159a4b1438ddf42a8fafc" } } ], "extra": [ 1, 234, 13, 62, 16, 149, 222, 183, 99, 128, 196, 108, 30, 197, 34, 160, 105, 86, 130, 208, 25, 235, 239, 122, 172, 209, 107, 235, 45, 73, 192, 33, 17, 2, 17, 0, 0, 0, 7, 51, 175, 153, 244, 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