Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 51b79abe3e6eee8ff94c627b07fc06c319d6ceb5d2641bb934c9004338b10192

Tx prefix hash: 4ba23bc2d3404ba5bfb1c6099d837ffad3f4b069ba9e50cdc9efe4693cddd562
Tx public key: badf4a60ff9a6ebdf1cd929ff175a09d73efa4a5b199158fcf9e1f67b26352b3
Timestamp: 1716986678 Timestamp [UCT]: 2024-05-29 12:44:38 Age [y:d:h:m:s]: 00:316:11:14:17
Block: 1032576 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 226177 RingCT/type: yes/0
Extra: 01badf4a60ff9a6ebdf1cd929ff175a09d73efa4a5b199158fcf9e1f67b26352b302110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 64b44ba9b4679fe5900fd879470d42c37fd59dd1378361b2873cf3deabcda965 0.600000000000 1501029 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": 1032586, "vin": [ { "gen": { "height": 1032576 } } ], "vout": [ { "amount": 600000000, "target": { "key": "64b44ba9b4679fe5900fd879470d42c37fd59dd1378361b2873cf3deabcda965" } } ], "extra": [ 1, 186, 223, 74, 96, 255, 154, 110, 189, 241, 205, 146, 159, 241, 117, 160, 157, 115, 239, 164, 165, 177, 153, 21, 143, 207, 158, 31, 103, 178, 99, 82, 179, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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