Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 57500f36ab12cb22e064f3f01ec3c815bb29c739a80f894b79766c1174205288

Tx prefix hash: a0530e195f280e23a8f7fa6ce5c135011b389a1bc8587f2cea11f19e8515cfc5
Tx public key: 7805ebc08dc56a7ec94c4c382d3071d92819db65f5aa6496d0c09cbac3b9a29f
Timestamp: 1713128436 Timestamp [UCT]: 2024-04-14 21:00:36 Age [y:d:h:m:s]: 01:044:15:30:32
Block: 1000572 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 292917 RingCT/type: yes/0
Extra: 017805ebc08dc56a7ec94c4c382d3071d92819db65f5aa6496d0c09cbac3b9a29f021100000006679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0f345c2c2329255885750c2b3c3616f3f745cc7198cf8d811f63af9f21133c60 0.600000000000 1461070 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": 1000582, "vin": [ { "gen": { "height": 1000572 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0f345c2c2329255885750c2b3c3616f3f745cc7198cf8d811f63af9f21133c60" } } ], "extra": [ 1, 120, 5, 235, 192, 141, 197, 106, 126, 201, 76, 76, 56, 45, 48, 113, 217, 40, 25, 219, 101, 245, 170, 100, 150, 208, 192, 156, 186, 195, 185, 162, 159, 2, 17, 0, 0, 0, 6, 103, 154, 138, 129, 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