Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc90b4a556f4b1e613ae1374b0b3413830a77bf6bbe8c9713ae726bb4e9566e2

Tx prefix hash: 2613c5a685de0f49dbea5f588ad1bf28a3b479bb79b0b6b5832b3665af104702
Tx public key: de90db8ed4489bf86cb7d287d89cbcf0c037da424b8dcb24912af2b9806d0096
Timestamp: 1756113218 Timestamp [UCT]: 2025-08-25 09:13:38 Age [y:d:h:m:s]: 00:157:21:15:09
Block: 1354031 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112689 RingCT/type: yes/0
Extra: 01de90db8ed4489bf86cb7d287d89cbcf0c037da424b8dcb24912af2b9806d00960211000000032609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d4af67f4dbaa4805027550753ebf0968b96cf2f037e879a095fc475af33bcb76 0.600000000000 1842012 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": 1354041, "vin": [ { "gen": { "height": 1354031 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d4af67f4dbaa4805027550753ebf0968b96cf2f037e879a095fc475af33bcb76" } } ], "extra": [ 1, 222, 144, 219, 142, 212, 72, 155, 248, 108, 183, 210, 135, 216, 156, 188, 240, 192, 55, 218, 66, 75, 141, 203, 36, 145, 42, 242, 185, 128, 109, 0, 150, 2, 17, 0, 0, 0, 3, 38, 9, 179, 160, 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