Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 53c99bcab4801f451b8acc34e6476f69b4a07732029bebd242a1d6755cb3ee4d

Tx prefix hash: f934df7d7d6c88128cb2e12f2d8faf3d16260901fb72bc57632ec81b9f315682
Tx public key: 9ef21bab0a6fefa8f84a3076318b66b89efbffb8fc6ca45fb8f71781947d59b1
Timestamp: 1736489935 Timestamp [UCT]: 2025-01-10 06:18:55 Age [y:d:h:m:s]: 00:088:01:17:14
Block: 1194129 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 62700 RingCT/type: yes/0
Extra: 019ef21bab0a6fefa8f84a3076318b66b89efbffb8fc6ca45fb8f71781947d59b1021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5529bd3c657374f82bb92d0dbc0e4499c65b8037d20c6404bb52ac068d3e207d 0.600000000000 1680696 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": 1194139, "vin": [ { "gen": { "height": 1194129 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5529bd3c657374f82bb92d0dbc0e4499c65b8037d20c6404bb52ac068d3e207d" } } ], "extra": [ 1, 158, 242, 27, 171, 10, 111, 239, 168, 248, 74, 48, 118, 49, 139, 102, 184, 158, 251, 255, 184, 252, 108, 164, 95, 184, 247, 23, 129, 148, 125, 89, 177, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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