Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8bac5a0790e020975dc20b03923c21e118e5b3694c83b565732f2b19448824d9

Tx prefix hash: 6fff43babfeb0c08cbbf41c3e63d48c46b4dc1ca4c44d95fd53f12bda940f203
Tx public key: 117d7d4d754c2eb1fb527e5eb8d685bf7ee75e899774cec82841202c0d34fab1
Timestamp: 1710265519 Timestamp [UCT]: 2024-03-12 17:45:19 Age [y:d:h:m:s]: 00:320:10:48:32
Block: 976859 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 229139 RingCT/type: yes/0
Extra: 01117d7d4d754c2eb1fb527e5eb8d685bf7ee75e899774cec82841202c0d34fab102110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bbd05f7ed52d00e37471d9a7dec47b0d44a291a8beb8cc05123cc65c778b2dcc 0.600000000000 1436858 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": 976869, "vin": [ { "gen": { "height": 976859 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bbd05f7ed52d00e37471d9a7dec47b0d44a291a8beb8cc05123cc65c778b2dcc" } } ], "extra": [ 1, 17, 125, 125, 77, 117, 76, 46, 177, 251, 82, 126, 94, 184, 214, 133, 191, 126, 231, 94, 137, 151, 116, 206, 200, 40, 65, 32, 44, 13, 52, 250, 177, 2, 17, 0, 0, 0, 1, 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