Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 746b6cd8f5599631c7578282b927c157a25585389c5ed2b7c0792cb3eaeb76da

Tx prefix hash: 7f05ad9a4cc586a27c94038f144d0ea3d20dd197825901a82ddc19fd841e43ba
Tx public key: 3c7e3ae65718bef8b71d564acefd043fc91c2f16324ee3978b57f02e0642ccd4
Timestamp: 1733973090 Timestamp [UCT]: 2024-12-12 03:11:30 Age [y:d:h:m:s]: 00:096:07:13:26
Block: 1173308 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68611 RingCT/type: yes/0
Extra: 013c7e3ae65718bef8b71d564acefd043fc91c2f16324ee3978b57f02e0642ccd4021100000001a2d75f44000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 46cc5b7928bab00ddda1855833e985ebf7a8aedf1c4d8d5c79576fa1e553462c 0.600000000000 1659317 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": 1173318, "vin": [ { "gen": { "height": 1173308 } } ], "vout": [ { "amount": 600000000, "target": { "key": "46cc5b7928bab00ddda1855833e985ebf7a8aedf1c4d8d5c79576fa1e553462c" } } ], "extra": [ 1, 60, 126, 58, 230, 87, 24, 190, 248, 183, 29, 86, 74, 206, 253, 4, 63, 201, 28, 47, 22, 50, 78, 227, 151, 139, 87, 240, 46, 6, 66, 204, 212, 2, 17, 0, 0, 0, 1, 162, 215, 95, 68, 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