Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7d1cf246ffc7f4d2363eae4672b7c5c136e639c2bfec9c2441ccb291c22c4357

Tx prefix hash: 3fd4a92ec439ca38e33a38bb70b3a2f1db720b9d2bf2e1d736cdf9acf0b549a5
Tx public key: 00b5a8b2e6f8964086517b95027c1a7a40bdd7223795b144632bb80428865c34
Timestamp: 1739727741 Timestamp [UCT]: 2025-02-16 17:42:21 Age [y:d:h:m:s]: 00:276:14:19:08
Block: 1220636 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 195471 RingCT/type: yes/0
Extra: 0100b5a8b2e6f8964086517b95027c1a7a40bdd7223795b144632bb80428865c34021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6750d8fd8c042d769727aeeea0870a22fb09901ba0ef45ed8786feb5f0a07b68 0.600000000000 1707477 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": 1220646, "vin": [ { "gen": { "height": 1220636 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6750d8fd8c042d769727aeeea0870a22fb09901ba0ef45ed8786feb5f0a07b68" } } ], "extra": [ 1, 0, 181, 168, 178, 230, 248, 150, 64, 134, 81, 123, 149, 2, 124, 26, 122, 64, 189, 215, 34, 55, 149, 177, 68, 99, 43, 184, 4, 40, 134, 92, 52, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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