Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 704074eb489bdead69c6786ea9eadf2cb292c2f95c3e7582a5528ec5486a97ee

Tx prefix hash: be3bbaded40a418489152b66bf7e41d8f28beb16e56a79a37763e5c98c01b1ec
Tx public key: 83e793a1b82de569877259a2c207b7e6ba64b0378d5a0ecea170227bde97576c
Timestamp: 1753579200 Timestamp [UCT]: 2025-07-27 01:20:00 Age [y:d:h:m:s]: 00:068:17:37:53
Block: 1334167 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 47892 RingCT/type: yes/0
Extra: 0183e793a1b82de569877259a2c207b7e6ba64b0378d5a0ecea170227bde97576c0211000000032609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9199ffd8ad1d6b66b96c67b3992ad131a780405c052c2c87d86e2ae7506377aa 0.600000000000 1821968 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": 1334177, "vin": [ { "gen": { "height": 1334167 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9199ffd8ad1d6b66b96c67b3992ad131a780405c052c2c87d86e2ae7506377aa" } } ], "extra": [ 1, 131, 231, 147, 161, 184, 45, 229, 105, 135, 114, 89, 162, 194, 7, 183, 230, 186, 100, 176, 55, 141, 90, 14, 206, 161, 112, 34, 123, 222, 151, 87, 108, 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