Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cbc977557579e6f1f9bfa3493e6b393f604dcdc5a5d645d73df3627874365ab0

Tx prefix hash: 3e39350f4b09eb508167a409e301cfee1e6b3570bb0df6d6feb0a50bc2a82ba2
Tx public key: bdee17dd312913d163cd681337a4d6503f16b29df49be9d9b6c6da9281c32225
Timestamp: 1736079780 Timestamp [UCT]: 2025-01-05 12:23:00 Age [y:d:h:m:s]: 00:092:06:44:23
Block: 1190739 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 65718 RingCT/type: yes/0
Extra: 01bdee17dd312913d163cd681337a4d6503f16b29df49be9d9b6c6da9281c32225021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6ecd04719092afb49e499536275e7f354993446dfe59c4e486d3f5cd2c26d693 0.600000000000 1677258 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": 1190749, "vin": [ { "gen": { "height": 1190739 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6ecd04719092afb49e499536275e7f354993446dfe59c4e486d3f5cd2c26d693" } } ], "extra": [ 1, 189, 238, 23, 221, 49, 41, 19, 209, 99, 205, 104, 19, 55, 164, 214, 80, 63, 22, 178, 157, 244, 155, 233, 217, 182, 198, 218, 146, 129, 195, 34, 37, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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