Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f5207f346f6f9823ec91eda49bf646dffb4727b641c28364f7434ec2ebbb286

Tx prefix hash: 1d7be266063be35a971cb7ed537441cef6028e5e0f3429bf6dee37dd0cd4ecd1
Tx public key: 294e30de43906eb0c7c0af2b494a80d0f0cfdf6e519169d6d549e920005745c7
Timestamp: 1747043098 Timestamp [UCT]: 2025-05-12 09:44:58 Age [y:d:h:m:s]: 00:193:04:23:56
Block: 1281223 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 135772 RingCT/type: yes/0
Extra: 01294e30de43906eb0c7c0af2b494a80d0f0cfdf6e519169d6d549e920005745c70211000000061f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3005a2a6fec5ce6bee851d7a87b29404fd16f3f794ed86afde533a5bae0efafd 0.600000000000 1768622 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": 1281233, "vin": [ { "gen": { "height": 1281223 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3005a2a6fec5ce6bee851d7a87b29404fd16f3f794ed86afde533a5bae0efafd" } } ], "extra": [ 1, 41, 78, 48, 222, 67, 144, 110, 176, 199, 192, 175, 43, 73, 74, 128, 208, 240, 207, 223, 110, 81, 145, 105, 214, 213, 73, 233, 32, 0, 87, 69, 199, 2, 17, 0, 0, 0, 6, 31, 144, 81, 122, 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