Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de9bea4a121eaa452de66ec45e1ebddb1c49cd6480a076a5ea9c7899fed7d0df

Tx prefix hash: 161934189c6729b431c0f4807d95278656fd327e0d86e5803aea89c60e9ec3e6
Tx public key: ff0d29e64b3ae9f54ef345f75773efa2f900e8b0deaa418f941d0ad7146a35ce
Timestamp: 1711733843 Timestamp [UCT]: 2024-03-29 17:37:23 Age [y:d:h:m:s]: 01:011:11:25:38
Block: 989041 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 269158 RingCT/type: yes/0
Extra: 01ff0d29e64b3ae9f54ef345f75773efa2f900e8b0deaa418f941d0ad7146a35ce02110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c6cc0edfdea0a1c3124c77e463828e07e5e24c703b9f9e2ce45ee854e1a3e8f9 0.600000000000 1449334 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": 989051, "vin": [ { "gen": { "height": 989041 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c6cc0edfdea0a1c3124c77e463828e07e5e24c703b9f9e2ce45ee854e1a3e8f9" } } ], "extra": [ 1, 255, 13, 41, 230, 75, 58, 233, 245, 78, 243, 69, 247, 87, 115, 239, 162, 249, 0, 232, 176, 222, 170, 65, 143, 148, 29, 10, 215, 20, 106, 53, 206, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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