Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ff17bca462ba39f2515d7bd72dffc0d16b2301b5197dfe64c0aa7c3c157d641

Tx prefix hash: b9a58710f809514c02a23a83e3226162d84ccbdb86ea97e74e53f1709e58231d
Tx public key: 46562aa6dbce08a7b387baacf33bcf7fa29027bc9fa2d2f5c8f58da8c4f0773a
Timestamp: 1750903395 Timestamp [UCT]: 2025-06-26 02:03:15 Age [y:d:h:m:s]: 00:139:06:02:37
Block: 1312885 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97491 RingCT/type: yes/0
Extra: 0146562aa6dbce08a7b387baacf33bcf7fa29027bc9fa2d2f5c8f58da8c4f0773a02110000000a43846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ac82d223d5bda1295aa226506ea924e675cd5240ccc7939ff3cf646dd260a5a6 0.600000000000 1800522 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": 1312895, "vin": [ { "gen": { "height": 1312885 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ac82d223d5bda1295aa226506ea924e675cd5240ccc7939ff3cf646dd260a5a6" } } ], "extra": [ 1, 70, 86, 42, 166, 219, 206, 8, 167, 179, 135, 186, 172, 243, 59, 207, 127, 162, 144, 39, 188, 159, 162, 210, 245, 200, 245, 141, 168, 196, 240, 119, 58, 2, 17, 0, 0, 0, 10, 67, 132, 109, 102, 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