Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af40a33c69347d8b250b57a8820f81c84d0759f33851d9a5332fe880abe56912

Tx prefix hash: 035199c3151b9e0958ec1ee4b6238fec0b67dea1c2f3f6cabb74f166c8efd76c
Tx public key: 7ecd7e705ad7f322f53a0d1e413e5b36c5e854e1c3c9f5922f272aff69c88a0b
Timestamp: 1745682470 Timestamp [UCT]: 2025-04-26 15:47:50 Age [y:d:h:m:s]: 00:016:06:35:18
Block: 1269964 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 11635 RingCT/type: yes/0
Extra: 017ecd7e705ad7f322f53a0d1e413e5b36c5e854e1c3c9f5922f272aff69c88a0b021100000002dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9370a8b3129d1ac5e0cb065059b49be8fa6e0e292ed059e364bdb31d9b1f436b 0.600000000000 1757203 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": 1269974, "vin": [ { "gen": { "height": 1269964 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9370a8b3129d1ac5e0cb065059b49be8fa6e0e292ed059e364bdb31d9b1f436b" } } ], "extra": [ 1, 126, 205, 126, 112, 90, 215, 243, 34, 245, 58, 13, 30, 65, 62, 91, 54, 197, 232, 84, 225, 195, 201, 245, 146, 47, 39, 42, 255, 105, 200, 138, 11, 2, 17, 0, 0, 0, 2, 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