Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 95f95e1f26bb2a04a3eb1a8ff357df59623e50b04c0ddb279ff97f8105dac9d6

Tx prefix hash: 80dbb2c51e925f1f7c4d753802c0e02140c13609b530282d2a599f0407cd4ffb
Tx public key: 2327d38d11fa3d1a3f0cd5272812f83f05383b58cf7f8efb958b09062df2957d
Timestamp: 1697546471 Timestamp [UCT]: 2023-10-17 12:41:11 Age [y:d:h:m:s]: 01:245:21:09:30
Block: 871605 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 436660 RingCT/type: yes/0
Extra: 012327d38d11fa3d1a3f0cd5272812f83f05383b58cf7f8efb958b09062df2957d02110000000833af99f4000000000000000000

1 output(s) for total of 0.794348061000 dcy

stealth address amount amount idx
00: b9e85a321f70e86892a691f245755a27d02e44aa971c375603c8918354057ba0 0.794348061000 1326606 of 0

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": 871615, "vin": [ { "gen": { "height": 871605 } } ], "vout": [ { "amount": 794348061, "target": { "key": "b9e85a321f70e86892a691f245755a27d02e44aa971c375603c8918354057ba0" } } ], "extra": [ 1, 35, 39, 211, 141, 17, 250, 61, 26, 63, 12, 213, 39, 40, 18, 248, 63, 5, 56, 59, 88, 207, 127, 142, 251, 149, 139, 9, 6, 45, 242, 149, 125, 2, 17, 0, 0, 0, 8, 51, 175, 153, 244, 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