Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0c9f6760b0f91c0a4dc3ff0198d3e2e689d9ce1b245f4ece9a28e358066af670

Tx prefix hash: b5c986c9d09b443a529dee038549a770e68ae8d97a5911f2c70d233536cd00ea
Tx public key: 81814f61d11ea6855400a12e2071e4ed0dcfac225c066597fc51904c38dfb3fa
Timestamp: 1733279524 Timestamp [UCT]: 2024-12-04 02:32:04 Age [y:d:h:m:s]: 00:335:03:37:55
Block: 1167544 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237051 RingCT/type: yes/0
Extra: 0181814f61d11ea6855400a12e2071e4ed0dcfac225c066597fc51904c38dfb3fa0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4b56d8b89e0d561ab856084ede53ff32f3f55dda5949a988e682cb3a609c0281 0.600000000000 1653241 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": 1167554, "vin": [ { "gen": { "height": 1167544 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b56d8b89e0d561ab856084ede53ff32f3f55dda5949a988e682cb3a609c0281" } } ], "extra": [ 1, 129, 129, 79, 97, 209, 30, 166, 133, 84, 0, 161, 46, 32, 113, 228, 237, 13, 207, 172, 34, 92, 6, 101, 151, 252, 81, 144, 76, 56, 223, 179, 250, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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