Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7412799e2cb43f818b3324bc6c22129f9b0d5d106ef4d370b7197d973a9b18e9

Tx prefix hash: 6ad5aafc50549ab28e0d5c9c91e279ccec19652d64962e1dcebebd41f75ea9e3
Tx public key: 57a748c4f37384f30a758e3a057043626e2baa2bca1dc10ee6f31ffbba8c1d76
Timestamp: 1727149029 Timestamp [UCT]: 2024-09-24 03:37:09 Age [y:d:h:m:s]: 00:174:07:39:50
Block: 1116825 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 124414 RingCT/type: yes/0
Extra: 0157a748c4f37384f30a758e3a057043626e2baa2bca1dc10ee6f31ffbba8c1d76021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e66f9afd43682224c5b7de4cac9ae65a4eab8fb54265f2c020bce319e0a22714 0.600000000000 1597444 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": 1116835, "vin": [ { "gen": { "height": 1116825 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e66f9afd43682224c5b7de4cac9ae65a4eab8fb54265f2c020bce319e0a22714" } } ], "extra": [ 1, 87, 167, 72, 196, 243, 115, 132, 243, 10, 117, 142, 58, 5, 112, 67, 98, 110, 43, 170, 43, 202, 29, 193, 14, 230, 243, 31, 251, 186, 140, 29, 118, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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