Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ddc99c19c7a55b2bd6879140a0e3ae81dbc19ee7df492f190d587a6f9cfdb40

Tx prefix hash: d97ef08d3ea9ed69cd0cac925ee394fe109cb0a10edd6f8afb46840f0c17a937
Tx public key: 52ae4cc51c0f7805d9acca283ea2f0128885c878a956fde61ee1422e745602e6
Timestamp: 1734427078 Timestamp [UCT]: 2024-12-17 09:17:58 Age [y:d:h:m:s]: 00:338:23:23:10
Block: 1177070 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 239754 RingCT/type: yes/0
Extra: 0152ae4cc51c0f7805d9acca283ea2f0128885c878a956fde61ee1422e745602e60211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1df0a94b2862c6b5c971597d48f6be440c78babede40ad1895d6dcad5da598bd 0.600000000000 1663433 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": 1177080, "vin": [ { "gen": { "height": 1177070 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1df0a94b2862c6b5c971597d48f6be440c78babede40ad1895d6dcad5da598bd" } } ], "extra": [ 1, 82, 174, 76, 197, 28, 15, 120, 5, 217, 172, 202, 40, 62, 162, 240, 18, 136, 133, 200, 120, 169, 86, 253, 230, 30, 225, 66, 46, 116, 86, 2, 230, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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