Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db6f57dc82d6e5f71f4eea17262471df5858e1bb369464dc2a8ea50a6fe7c7ef

Tx prefix hash: 33a0fb4934d689c900d261a25757ee50eef3de56aac3e845edf66aa1d6b08ea3
Tx public key: aeafab1e45749b0b0c37349f04986c97021c20b28bc18cdedc54cd93d9c664d6
Timestamp: 1726650155 Timestamp [UCT]: 2024-09-18 09:02:35 Age [y:d:h:m:s]: 00:236:18:52:25
Block: 1112682 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 169078 RingCT/type: yes/0
Extra: 01aeafab1e45749b0b0c37349f04986c97021c20b28bc18cdedc54cd93d9c664d6021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b2655f47630f7f4c831981afc51f210dba1bc60fa1d4b3faec5f856ec42633ce 0.600000000000 1592089 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": 1112692, "vin": [ { "gen": { "height": 1112682 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b2655f47630f7f4c831981afc51f210dba1bc60fa1d4b3faec5f856ec42633ce" } } ], "extra": [ 1, 174, 175, 171, 30, 69, 116, 155, 11, 12, 55, 52, 159, 4, 152, 108, 151, 2, 28, 32, 178, 139, 193, 140, 222, 220, 84, 205, 147, 217, 198, 100, 214, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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