Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd290165a3979464869e2ab599877275809dd52d65b29a4a2b6d95471146e68d

Tx prefix hash: c62e2a84e6014ea86a179cb07f8d604503a00f78fc2a646f8e2d966c7c438825
Tx public key: 04f8160ef50302e4c6a70712fde96eed5d5b6737bfdb8d1918a3eaaf22126ec9
Timestamp: 1578927579 Timestamp [UCT]: 2020-01-13 14:59:39 Age [y:d:h:m:s]: 04:318:17:50:18
Block: 44740 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1117270 RingCT/type: yes/0
Extra: 0104f8160ef50302e4c6a70712fde96eed5d5b6737bfdb8d1918a3eaaf22126ec90211000000114ac5aa02000000000000000000

1 output(s) for total of 436.290423388000 dcy

stealth address amount amount idx
00: 31b5b2d6fdad9948f17c63d17d75bddb794e8aa69cbb6ae81769d2dea0f35de9 436.290423388000 81496 of 0

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": 44750, "vin": [ { "gen": { "height": 44740 } } ], "vout": [ { "amount": 436290423388, "target": { "key": "31b5b2d6fdad9948f17c63d17d75bddb794e8aa69cbb6ae81769d2dea0f35de9" } } ], "extra": [ 1, 4, 248, 22, 14, 245, 3, 2, 228, 198, 167, 7, 18, 253, 233, 110, 237, 93, 91, 103, 55, 191, 219, 141, 25, 24, 163, 234, 175, 34, 18, 110, 201, 2, 17, 0, 0, 0, 17, 74, 197, 170, 2, 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