Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 30d3628f7e5ac895df1f0f44102c45861a5f34846b1c878a77b89b74a8c1899c

Tx prefix hash: 852993b1ff59efe515e0ca0efebc10d128bcc1a898d9662057b8c1cc49484a47
Tx public key: 0442be1d83013070e44d1296d23960228727e345e9ca3aca5893dee9937d9aa7
Timestamp: 1736118879 Timestamp [UCT]: 2025-01-05 23:14:39 Age [y:d:h:m:s]: 00:305:00:14:32
Block: 1191059 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 215473 RingCT/type: yes/0
Extra: 010442be1d83013070e44d1296d23960228727e345e9ca3aca5893dee9937d9aa70211000000181f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ee09e1e33329edd62723df8cef5b2664df31e88f2e50f4a5096ce8f22d3b06f2 0.600000000000 1677582 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": 1191069, "vin": [ { "gen": { "height": 1191059 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ee09e1e33329edd62723df8cef5b2664df31e88f2e50f4a5096ce8f22d3b06f2" } } ], "extra": [ 1, 4, 66, 190, 29, 131, 1, 48, 112, 228, 77, 18, 150, 210, 57, 96, 34, 135, 39, 227, 69, 233, 202, 58, 202, 88, 147, 222, 233, 147, 125, 154, 167, 2, 17, 0, 0, 0, 24, 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