Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 65f86fbe565c1c894a6f187ec8ff2578e7c89a5c6af99de8888a14486073b616

Tx prefix hash: 4e621d6daf5d076967c27f1b188cc9ca04d13cf5524966fbada33e3b885fe863
Tx public key: 9fb9905f78a18a75db8657c8e80b3ec2abbdd8b9663822b0ab420e2eb99a5f8c
Timestamp: 1756207097 Timestamp [UCT]: 2025-08-26 11:18:17 Age [y:d:h:m:s]: 00:135:09:54:43
Block: 1354808 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 96781 RingCT/type: yes/0
Extra: 019fb9905f78a18a75db8657c8e80b3ec2abbdd8b9663822b0ab420e2eb99a5f8c0211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b165a799ba7ed3e33032fd41ce95548c0870f88af3c35e5ebf6e25ed86e0321b 0.600000000000 1842803 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": 1354818, "vin": [ { "gen": { "height": 1354808 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b165a799ba7ed3e33032fd41ce95548c0870f88af3c35e5ebf6e25ed86e0321b" } } ], "extra": [ 1, 159, 185, 144, 95, 120, 161, 138, 117, 219, 134, 87, 200, 232, 11, 62, 194, 171, 189, 216, 185, 102, 56, 34, 176, 171, 66, 14, 46, 185, 154, 95, 140, 2, 17, 0, 0, 0, 2, 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