Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e2c4f8626e4ddf58b18201802e7de2686d2293bf948854b37d29e3bff4d299ad

Tx prefix hash: 662223ee9eb7cd4494115ee0ae597afdea81aef7abc94b595aed5444be648edd
Tx public key: af7e6cbca8d141dee5ba605c9b1452a8f06c7001fbfa710d43fdd4c8f99b9c07
Timestamp: 1745666651 Timestamp [UCT]: 2025-04-26 11:24:11 Age [y:d:h:m:s]: 00:205:10:43:57
Block: 1269837 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 144537 RingCT/type: yes/0
Extra: 01af7e6cbca8d141dee5ba605c9b1452a8f06c7001fbfa710d43fdd4c8f99b9c07021100000009dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f77622c00c7e7c4d7423517c57a4570a842b1f07431d323acdb2027d97c97520 0.600000000000 1757076 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": 1269847, "vin": [ { "gen": { "height": 1269837 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f77622c00c7e7c4d7423517c57a4570a842b1f07431d323acdb2027d97c97520" } } ], "extra": [ 1, 175, 126, 108, 188, 168, 209, 65, 222, 229, 186, 96, 92, 155, 20, 82, 168, 240, 108, 112, 1, 251, 250, 113, 13, 67, 253, 212, 200, 249, 155, 156, 7, 2, 17, 0, 0, 0, 9, 219, 181, 113, 193, 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