Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a66106997b2da520979366e8998425a0f188bbac3f5c2dc377b4010931651196

Tx prefix hash: 96d5e49ea7c3022d990d402d4f2299775cfa279a87353209930578dd26682b73
Tx public key: 710a381ebf4a41ec017902c37a6d0bb7f3dad9cb73af9150b994c1e39912bee9
Timestamp: 1737201926 Timestamp [UCT]: 2025-01-18 12:05:26 Age [y:d:h:m:s]: 00:151:05:15:39
Block: 1200014 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107782 RingCT/type: yes/0
Extra: 01710a381ebf4a41ec017902c37a6d0bb7f3dad9cb73af9150b994c1e39912bee90211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fb7b1c1bde6cd19d06c277251d2346ac34d23cb7a4622342e0f3d916f1cd29f5 0.600000000000 1686655 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": 1200024, "vin": [ { "gen": { "height": 1200014 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fb7b1c1bde6cd19d06c277251d2346ac34d23cb7a4622342e0f3d916f1cd29f5" } } ], "extra": [ 1, 113, 10, 56, 30, 191, 74, 65, 236, 1, 121, 2, 195, 122, 109, 11, 183, 243, 218, 217, 203, 115, 175, 145, 80, 185, 148, 193, 227, 153, 18, 190, 233, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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