Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eaf935f5602ac752e3da0382471813a0f3c549ac312f282f8903731bae4ecee1

Tx prefix hash: 326675f7783f989d64670f32d88d6985ff49f5621c4d5dd7c5e6f1890b494509
Tx public key: c040b7b4c16d06b5ee5da93523d88675096ca3a436a683d6c51f5574231fe5f7
Timestamp: 1733931939 Timestamp [UCT]: 2024-12-11 15:45:39 Age [y:d:h:m:s]: 00:103:18:00:33
Block: 1172958 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 73929 RingCT/type: yes/0
Extra: 01c040b7b4c16d06b5ee5da93523d88675096ca3a436a683d6c51f5574231fe5f70211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1d8532ea5bb410744f0fd3f01007f680b72b48e3a5871b9928c28a45479f0460 0.600000000000 1658921 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": 1172968, "vin": [ { "gen": { "height": 1172958 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d8532ea5bb410744f0fd3f01007f680b72b48e3a5871b9928c28a45479f0460" } } ], "extra": [ 1, 192, 64, 183, 180, 193, 109, 6, 181, 238, 93, 169, 53, 35, 216, 134, 117, 9, 108, 163, 164, 54, 166, 131, 214, 197, 31, 85, 116, 35, 31, 229, 247, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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