Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: adcb92b682a3da50712714d8dd1c52a0d658896ce5b3711fcc717f8b88c4d0eb

Tx prefix hash: d0b1d248cc8bfec6dc2c7fff93993e7a7f61679a7efa57de572078398368b42b
Tx public key: 966a8cfb8cf196b3d2d8066a879edfd9522a8bf4fdde50983171775e74a64849
Timestamp: 1750430885 Timestamp [UCT]: 2025-06-20 14:48:05 Age [y:d:h:m:s]: 00:153:07:02:13
Block: 1309109 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107403 RingCT/type: yes/0
Extra: 01966a8cfb8cf196b3d2d8066a879edfd9522a8bf4fdde50983171775e74a648490211000000028368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7141ac0f919e22a260b9c2aa81ef6b062fdddbc976e670361dfd7e382b505192 0.600000000000 1796724 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": 1309119, "vin": [ { "gen": { "height": 1309109 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7141ac0f919e22a260b9c2aa81ef6b062fdddbc976e670361dfd7e382b505192" } } ], "extra": [ 1, 150, 106, 140, 251, 140, 241, 150, 179, 210, 216, 6, 106, 135, 158, 223, 217, 82, 42, 139, 244, 253, 222, 80, 152, 49, 113, 119, 94, 116, 166, 72, 73, 2, 17, 0, 0, 0, 2, 131, 104, 38, 109, 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