Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 86f5da420104e9bf2e392961429f62bbf90f6b27ea7e20df88b1e995a791e673

Tx prefix hash: e6890931c26195bb97442650fa3f8a0b48427ab9bc6104a3e88530b8c8790e71
Tx public key: 03c353f016b2e984d9e6440b3d798458b126728bc58e1a3987d5f30e5b77f417
Timestamp: 1714358405 Timestamp [UCT]: 2024-04-29 02:40:05 Age [y:d:h:m:s]: 01:007:16:34:15
Block: 1010782 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 266433 RingCT/type: yes/0
Extra: 0103c353f016b2e984d9e6440b3d798458b126728bc58e1a3987d5f30e5b77f4170211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4efd9562afa42134e994849aec573961587a8e0ac30bbf5b9bea238d5a33ff9e 0.600000000000 1472830 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": 1010792, "vin": [ { "gen": { "height": 1010782 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4efd9562afa42134e994849aec573961587a8e0ac30bbf5b9bea238d5a33ff9e" } } ], "extra": [ 1, 3, 195, 83, 240, 22, 178, 233, 132, 217, 230, 68, 11, 61, 121, 132, 88, 177, 38, 114, 139, 197, 142, 26, 57, 135, 213, 243, 14, 91, 119, 244, 23, 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