Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1dc80e7da50b1679098ff25cef153eed9166faf837e991434f3e437b36c7fd5e

Tx prefix hash: 63e4a4c2884db7c4443719d4558fc4301ce1c268f082f051544cbc030a9af75c
Tx public key: f158e2ef698a46c4bf41897230c257d2ff9c98b13f8f16f1ac267ed8daa279db
Timestamp: 1705992228 Timestamp [UCT]: 2024-01-23 06:43:48 Age [y:d:h:m:s]: 01:113:16:10:56
Block: 941387 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 342371 RingCT/type: yes/0
Extra: 01f158e2ef698a46c4bf41897230c257d2ff9c98b13f8f16f1ac267ed8daa279db02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6864e6af9aa03fd45b0c02f7c8c576e3b35aeb589c42396757cd3d1d153cbc04 0.600000000000 1399533 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": 941397, "vin": [ { "gen": { "height": 941387 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6864e6af9aa03fd45b0c02f7c8c576e3b35aeb589c42396757cd3d1d153cbc04" } } ], "extra": [ 1, 241, 88, 226, 239, 105, 138, 70, 196, 191, 65, 137, 114, 48, 194, 87, 210, 255, 156, 152, 177, 63, 143, 22, 241, 172, 38, 126, 216, 218, 162, 121, 219, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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