Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3d382031a3cc07a08a71283a8e2e0da26f52dc5f02a001dcbf3fdb539da92789

Tx prefix hash: ab2db57abf148501ee26048d73bd1a903e9758f453d64d5bb7ac5c79c2ee9f3e
Tx public key: 3e75ce32391ecdbaac2c2c11f12b0fe61ef4584fbbbb4a5c8fbe41872f96c21b
Timestamp: 1681238934 Timestamp [UCT]: 2023-04-11 18:48:54 Age [y:d:h:m:s]: 01:360:21:50:50
Block: 736446 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 519225 RingCT/type: yes/0
Extra: 013e75ce32391ecdbaac2c2c11f12b0fe61ef4584fbbbb4a5c8fbe41872f96c21b0211000000045029cbac000000000000000000

1 output(s) for total of 2.227660026000 dcy

stealth address amount amount idx
00: 1be8033b7845e8ffc56ec3abb47afe59bd759b9d0fbaef07d033dc4277544195 2.227660026000 1182881 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": 736456, "vin": [ { "gen": { "height": 736446 } } ], "vout": [ { "amount": 2227660026, "target": { "key": "1be8033b7845e8ffc56ec3abb47afe59bd759b9d0fbaef07d033dc4277544195" } } ], "extra": [ 1, 62, 117, 206, 50, 57, 30, 205, 186, 172, 44, 44, 17, 241, 43, 15, 230, 30, 244, 88, 79, 187, 187, 74, 92, 143, 190, 65, 135, 47, 150, 194, 27, 2, 17, 0, 0, 0, 4, 80, 41, 203, 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