Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 401881b16325c69d8364f375be9cdccd5f5f6834465704a603ca5fbdfe4ea041

Tx prefix hash: e73e403c6359f45890e975d5044e8e09532e48e15cc90443d251dd066b55517b
Tx public key: 8aec1d4b8e90d6cae105061045a3ff1cefcc7a2efccc3b61aaac5a789874360d
Timestamp: 1756299610 Timestamp [UCT]: 2025-08-27 13:00:10 Age [y:d:h:m:s]: 00:134:05:29:02
Block: 1355581 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 95928 RingCT/type: yes/0
Extra: 018aec1d4b8e90d6cae105061045a3ff1cefcc7a2efccc3b61aaac5a789874360d0211000000032609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 202bd4d4ba1c9c34388a6a391ba75595d3f048ab77ab73ecd9877e65bbad93a9 0.600000000000 1843582 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": 1355591, "vin": [ { "gen": { "height": 1355581 } } ], "vout": [ { "amount": 600000000, "target": { "key": "202bd4d4ba1c9c34388a6a391ba75595d3f048ab77ab73ecd9877e65bbad93a9" } } ], "extra": [ 1, 138, 236, 29, 75, 142, 144, 214, 202, 225, 5, 6, 16, 69, 163, 255, 28, 239, 204, 122, 46, 252, 204, 59, 97, 170, 172, 90, 120, 152, 116, 54, 13, 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