Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 95dc4831b6fae2939c6969b94c70ae4a76c4eef699aa27c674c86945d4a834ce

Tx prefix hash: 8a39c252122582b50fe4ac987e1085e0c7b5fc9150eed3d2d7b507be6e98c21a
Tx public key: 325a9807a927cb81dd5896395e8050917efd33e2c0a2a42d393f40d3002b3dc3
Timestamp: 1703686198 Timestamp [UCT]: 2023-12-27 14:09:58 Age [y:d:h:m:s]: 01:015:16:09:46
Block: 922306 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 272542 RingCT/type: yes/0
Extra: 01325a9807a927cb81dd5896395e8050917efd33e2c0a2a42d393f40d3002b3dc302110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b58880800c13152b354d99a03af27b95271acfdaca3692cfdd64a81d723e1da0 0.600000000000 1380002 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": 922316, "vin": [ { "gen": { "height": 922306 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b58880800c13152b354d99a03af27b95271acfdaca3692cfdd64a81d723e1da0" } } ], "extra": [ 1, 50, 90, 152, 7, 169, 39, 203, 129, 221, 88, 150, 57, 94, 128, 80, 145, 126, 253, 51, 226, 192, 162, 164, 45, 57, 63, 64, 211, 0, 43, 61, 195, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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