Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aeb8047ab28e832c9c1f367ceebbaab2ffd33fc652245468b0c0c48c11e0c679

Tx prefix hash: 63fc64b18c4905d47e9818c73cd6a3f0bbfade6136c10fbbd8cecbe8cd58c50f
Tx public key: bc00a2b51422644f7ea6a2598a0029896df231e66d55d7e92fda4b36a792a6d1
Timestamp: 1763509994 Timestamp [UCT]: 2025-11-18 23:53:14 Age [y:d:h:m:s]: 00:009:05:59:41
Block: 1415151 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 6620 RingCT/type: yes/0
Extra: 01bc00a2b51422644f7ea6a2598a0029896df231e66d55d7e92fda4b36a792a6d10211000000027b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ee40432f765247824b052c63cb2c159fc80a0d22e85d0c4bee38fe0c55ff79ab 0.600000000000 1903646 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": 1415161, "vin": [ { "gen": { "height": 1415151 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ee40432f765247824b052c63cb2c159fc80a0d22e85d0c4bee38fe0c55ff79ab" } } ], "extra": [ 1, 188, 0, 162, 181, 20, 34, 100, 79, 126, 166, 162, 89, 138, 0, 41, 137, 109, 242, 49, 230, 109, 85, 215, 233, 47, 218, 75, 54, 167, 146, 166, 209, 2, 17, 0, 0, 0, 2, 123, 30, 81, 172, 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