Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 658d5b57f062afffce273ccb6464d466f62e63df418ea532ec70bdfe9c594850

Tx prefix hash: e5f5e817828c42d88e02bdfc2b7564c1ba481347d203cdac4c8de9aea8109d42
Tx public key: c3c27ae9f4596e034d878ae5304fe621e21c8e52aca78bc2117e8a3764fc100c
Timestamp: 1677780935 Timestamp [UCT]: 2023-03-02 18:15:35 Age [y:d:h:m:s]: 02:091:00:31:00
Block: 708421 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 586670 RingCT/type: yes/0
Extra: 01c3c27ae9f4596e034d878ae5304fe621e21c8e52aca78bc2117e8a3764fc100c0211000000025029cbac000000000000000000

1 output(s) for total of 2.758716347000 dcy

stealth address amount amount idx
00: 4cbdbbb10a976263c1ce1161d1d38300e4ddb532fb609c68b6be2d34444028c6 2.758716347000 1152312 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": 708431, "vin": [ { "gen": { "height": 708421 } } ], "vout": [ { "amount": 2758716347, "target": { "key": "4cbdbbb10a976263c1ce1161d1d38300e4ddb532fb609c68b6be2d34444028c6" } } ], "extra": [ 1, 195, 194, 122, 233, 244, 89, 110, 3, 77, 135, 138, 229, 48, 79, 230, 33, 226, 28, 142, 82, 172, 167, 139, 194, 17, 126, 138, 55, 100, 252, 16, 12, 2, 17, 0, 0, 0, 2, 80, 41, 203, 172, 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