Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 81e63526d90448c8e80d12f3d0e555160602612b54493c8eaf0746b7971700bd

Tx prefix hash: a8682c33da7cad6c19a4b9cd22596244bfdd2fc5a6fbf11221736ce7271c8cba
Tx public key: bdcd7e83e4a139f8838285d7c565ec231d4a8988e66f85f9042e6fcecfb06d54
Timestamp: 1702792900 Timestamp [UCT]: 2023-12-17 06:01:40 Age [y:d:h:m:s]: 01:185:10:46:49
Block: 914899 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 393593 RingCT/type: yes/0
Extra: 01bdcd7e83e4a139f8838285d7c565ec231d4a8988e66f85f9042e6fcecfb06d54021100000002e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8865c772a02421a4d85a92b594cbd0d12dcf2bf50f11c905550e21932e7ef13e 0.600000000000 1372253 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": 914909, "vin": [ { "gen": { "height": 914899 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8865c772a02421a4d85a92b594cbd0d12dcf2bf50f11c905550e21932e7ef13e" } } ], "extra": [ 1, 189, 205, 126, 131, 228, 161, 57, 248, 131, 130, 133, 215, 197, 101, 236, 35, 29, 74, 137, 136, 230, 111, 133, 249, 4, 46, 111, 206, 207, 176, 109, 84, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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