Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa430db2a5382af60e24c5493580fb2bf72193208edd7a972f4220484fc4abf5

Tx prefix hash: b324641e4acfd711b2ca26282ad0eb1c5056fd698dee42b0f0d80d65cef27c0b
Tx public key: 1a9081791268d31f07a8c2b73552a7c2b8aa3552a235ada99a62397c010fdb34
Timestamp: 1727969313 Timestamp [UCT]: 2024-10-03 15:28:33 Age [y:d:h:m:s]: 00:247:04:03:15
Block: 1123631 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176492 RingCT/type: yes/0
Extra: 011a9081791268d31f07a8c2b73552a7c2b8aa3552a235ada99a62397c010fdb34021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9f68043653b4bf62fa5feda484a0c8c72bb203158843d2a938fda6dcdb42dad8 0.600000000000 1606166 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": 1123641, "vin": [ { "gen": { "height": 1123631 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9f68043653b4bf62fa5feda484a0c8c72bb203158843d2a938fda6dcdb42dad8" } } ], "extra": [ 1, 26, 144, 129, 121, 18, 104, 211, 31, 7, 168, 194, 183, 53, 82, 167, 194, 184, 170, 53, 82, 162, 53, 173, 169, 154, 98, 57, 124, 1, 15, 219, 52, 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