Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 020322b156ab9b2ae99785f27d205bd84f40d9f3ee5902e5d3f4e07a0c61b6d9

Tx prefix hash: aa02e11b1a91bb39d1c4830fa2c3c6178c5fd93f9564814d1ad3afe2e5114114
Tx public key: 2e0d38b20008cdd140683150126540ec85a9fe06ffdd4093c1dccade3ac2e91a
Timestamp: 1736497883 Timestamp [UCT]: 2025-01-10 08:31:23 Age [y:d:h:m:s]: 00:345:23:51:20
Block: 1194187 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 244836 RingCT/type: yes/0
Extra: 012e0d38b20008cdd140683150126540ec85a9fe06ffdd4093c1dccade3ac2e91a0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 00a0a628f6c9b97ad0620f5558341cc0e00d251197fcf35a9f2758b0386c940a 0.600000000000 1680754 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": 1194197, "vin": [ { "gen": { "height": 1194187 } } ], "vout": [ { "amount": 600000000, "target": { "key": "00a0a628f6c9b97ad0620f5558341cc0e00d251197fcf35a9f2758b0386c940a" } } ], "extra": [ 1, 46, 13, 56, 178, 0, 8, 205, 209, 64, 104, 49, 80, 18, 101, 64, 236, 133, 169, 254, 6, 255, 221, 64, 147, 193, 220, 202, 222, 58, 194, 233, 26, 2, 17, 0, 0, 0, 2, 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