Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 35bf09f8ae0db20813c6b530f8837dbada6937c1a16a608b173000515b11821b

Tx prefix hash: ede612e84c618888a5975d371e20498d9fedf5498a50e5723690e87987dddf1c
Tx public key: 91f67bbc39ef53fb515729e5256327ad5e9f210e6fb034ff3aa2f4ad823a98ce
Timestamp: 1737809539 Timestamp [UCT]: 2025-01-25 12:52:19 Age [y:d:h:m:s]: 00:143:13:46:58
Block: 1205013 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102344 RingCT/type: yes/0
Extra: 0191f67bbc39ef53fb515729e5256327ad5e9f210e6fb034ff3aa2f4ad823a98ce021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 527e24b6fb52f7a321d1359c496c5521cde57660423435a7a9c4a6d17a3f8cef 0.600000000000 1691708 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": 1205023, "vin": [ { "gen": { "height": 1205013 } } ], "vout": [ { "amount": 600000000, "target": { "key": "527e24b6fb52f7a321d1359c496c5521cde57660423435a7a9c4a6d17a3f8cef" } } ], "extra": [ 1, 145, 246, 123, 188, 57, 239, 83, 251, 81, 87, 41, 229, 37, 99, 39, 173, 94, 159, 33, 14, 111, 176, 52, 255, 58, 162, 244, 173, 130, 58, 152, 206, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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