Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 36afd4ece417720a4a84dfbd16b98723c02050dab3fab0c9af60ba3e8b9b2768

Tx prefix hash: 7653e3c21d6f77b51d5c6febe8c7cc56b77534f010ea676ebaf4d7bb7a33fb8e
Tx public key: 6f5c7e99a5d7dcb28db85ff9c6598c8caebad90d9ecda70c899e767b68c8c2f6
Timestamp: 1728033980 Timestamp [UCT]: 2024-10-04 09:26:20 Age [y:d:h:m:s]: 00:255:19:02:40
Block: 1124168 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182538 RingCT/type: yes/0
Extra: 016f5c7e99a5d7dcb28db85ff9c6598c8caebad90d9ecda70c899e767b68c8c2f602110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1558622957beefd0b9497e6c84dc008c02c1e15a6f9623dc94ac78ae0b9c2101 0.600000000000 1606749 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": 1124178, "vin": [ { "gen": { "height": 1124168 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1558622957beefd0b9497e6c84dc008c02c1e15a6f9623dc94ac78ae0b9c2101" } } ], "extra": [ 1, 111, 92, 126, 153, 165, 215, 220, 178, 141, 184, 95, 249, 198, 89, 140, 140, 174, 186, 217, 13, 158, 205, 167, 12, 137, 158, 118, 123, 104, 200, 194, 246, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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