Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 54fd1f0b5b80a684305c1c5510d698e5db78ffd694e31e1a89c7520eb7213872

Tx prefix hash: c32b7e10904663a1a10602e504cc9ccdd9626e184cf8cc7d91c357a0dafb4241
Tx public key: f3978ad170689a505789c5103f89ac9e0f82a232062f78718c569aba0f0f27db
Timestamp: 1704746117 Timestamp [UCT]: 2024-01-08 20:35:17 Age [y:d:h:m:s]: 01:049:02:36:10
Block: 931077 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 296177 RingCT/type: yes/0
Extra: 01f3978ad170689a505789c5103f89ac9e0f82a232062f78718c569aba0f0f27db0211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c7cbfa3e7db51ddee9dfaeabe6665dc2b5ca2eb9b86f1f021a32221b2c97f29f 0.600000000000 1388969 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": 931087, "vin": [ { "gen": { "height": 931077 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c7cbfa3e7db51ddee9dfaeabe6665dc2b5ca2eb9b86f1f021a32221b2c97f29f" } } ], "extra": [ 1, 243, 151, 138, 209, 112, 104, 154, 80, 87, 137, 197, 16, 63, 137, 172, 158, 15, 130, 162, 50, 6, 47, 120, 113, 140, 86, 154, 186, 15, 15, 39, 219, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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