Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 69651d0cb3c804751676e52fa0970aa89158929dcc8c71ddaa97705178cd718f

Tx prefix hash: ebc8c5d4ada2e526aa3abfa4e4172469516107e1bd8af0ad1f22918358507a68
Tx public key: fef3fc283bc01c5a99ba5ea4c427f7912a05b031f0309fb01f84e706c37e83b7
Timestamp: 1755927592 Timestamp [UCT]: 2025-08-23 05:39:52 Age [y:d:h:m:s]: 00:084:20:48:18
Block: 1352486 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 60593 RingCT/type: yes/0
Extra: 01fef3fc283bc01c5a99ba5ea4c427f7912a05b031f0309fb01f84e706c37e83b70211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 94d007c6feb22aae60b3748789dd84cf2fb0a56488589570c3e9f49722af0c92 0.600000000000 1840451 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": 1352496, "vin": [ { "gen": { "height": 1352486 } } ], "vout": [ { "amount": 600000000, "target": { "key": "94d007c6feb22aae60b3748789dd84cf2fb0a56488589570c3e9f49722af0c92" } } ], "extra": [ 1, 254, 243, 252, 40, 59, 192, 28, 90, 153, 186, 94, 164, 196, 39, 247, 145, 42, 5, 176, 49, 240, 48, 159, 176, 31, 132, 231, 6, 195, 126, 131, 183, 2, 17, 0, 0, 0, 1, 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