Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a236f07e45b187412ad822e861b3bf975b6762c8f5d0e92f16804ef37c196ab2

Tx prefix hash: 8d126e8ac196d9daa71ee8d73863d093acc6bcfdf1219609e27e46374a14b357
Tx public key: 46deb2c2cd343144b9c29540aef12d5ad4298bdabd0655dc0d4fdddb58099f1a
Timestamp: 1761752907 Timestamp [UCT]: 2025-10-29 15:48:27 Age [y:d:h:m:s]: 00:067:00:45:29
Block: 1400591 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 48007 RingCT/type: yes/0
Extra: 0146deb2c2cd343144b9c29540aef12d5ad4298bdabd0655dc0d4fdddb58099f1a0211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1b39e347bad5cada7c7644e65abb30ec5aa876a789c4c1e26cae15bcd53422f5 0.600000000000 1888908 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": 1400601, "vin": [ { "gen": { "height": 1400591 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b39e347bad5cada7c7644e65abb30ec5aa876a789c4c1e26cae15bcd53422f5" } } ], "extra": [ 1, 70, 222, 178, 194, 205, 52, 49, 68, 185, 194, 149, 64, 174, 241, 45, 90, 212, 41, 139, 218, 189, 6, 85, 220, 13, 79, 221, 219, 88, 9, 159, 26, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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