Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a5f6306773d91c4b3154e735eae0365e952be2a01071409e9bdf8c49b8b1c268

Tx prefix hash: 8ac98b537ef313679217404a616437488d14beae3c6cf2c4088f2bf3ddcfbc67
Tx public key: f3a549717822730259c41d1bc5442d7fdb5f9b6564df34bbe2ebaa8e8ee4375c
Timestamp: 1730206496 Timestamp [UCT]: 2024-10-29 12:54:56 Age [y:d:h:m:s]: 00:085:13:48:28
Block: 1142111 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 61161 RingCT/type: yes/0
Extra: 01f3a549717822730259c41d1bc5442d7fdb5f9b6564df34bbe2ebaa8e8ee4375c0211000000023cd0fc06000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 99b9dbdc96a595a2d0ee80ee8a86b42301ab36bf0efdb1f5bedbe08084edec09 0.600000000000 1625948 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": 1142121, "vin": [ { "gen": { "height": 1142111 } } ], "vout": [ { "amount": 600000000, "target": { "key": "99b9dbdc96a595a2d0ee80ee8a86b42301ab36bf0efdb1f5bedbe08084edec09" } } ], "extra": [ 1, 243, 165, 73, 113, 120, 34, 115, 2, 89, 196, 29, 27, 197, 68, 45, 127, 219, 95, 155, 101, 100, 223, 52, 187, 226, 235, 170, 142, 142, 228, 55, 92, 2, 17, 0, 0, 0, 2, 60, 208, 252, 6, 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