Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b85e9ece38eff7c366b49408fada4c7d128c6ca2d262de22e74bf6940db15025

Tx prefix hash: 7fd4ca576076185e3549e5f25fc9aecf637637e54995a4d942876406c6dd861a
Tx public key: a1c13a7f4778b9caea3dd49d37c5081ee8db029d6baefea7179668773eb3e481
Timestamp: 1703802405 Timestamp [UCT]: 2023-12-28 22:26:45 Age [y:d:h:m:s]: 01:317:22:55:07
Block: 923273 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 486072 RingCT/type: yes/0
Extra: 01a1c13a7f4778b9caea3dd49d37c5081ee8db029d6baefea7179668773eb3e481021100000004ad5694ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 013a612bcde9aa6c01c976f55eac8865b4f6dc186e8d0c9582f4cf32db230565 0.600000000000 1381001 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": 923283, "vin": [ { "gen": { "height": 923273 } } ], "vout": [ { "amount": 600000000, "target": { "key": "013a612bcde9aa6c01c976f55eac8865b4f6dc186e8d0c9582f4cf32db230565" } } ], "extra": [ 1, 161, 193, 58, 127, 71, 120, 185, 202, 234, 61, 212, 157, 55, 197, 8, 30, 232, 219, 2, 157, 107, 174, 254, 167, 23, 150, 104, 119, 62, 179, 228, 129, 2, 17, 0, 0, 0, 4, 173, 86, 148, 172, 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