Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 603fb64a3c3e3b53b6583c6a4fc7ece371430a867c2647575fd439e0413321f7

Tx prefix hash: a6aac65ec5ce3814af6722cabbeaed4e013aba02dd553962a421ee9e2b6a377d
Tx public key: 9402fcbb84ad7801d93e7f9178cbcf277051a2afe8d1b40cd1aa8e6fc972863d
Timestamp: 1703765203 Timestamp [UCT]: 2023-12-28 12:06:43 Age [y:d:h:m:s]: 01:176:07:22:32
Block: 922964 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 386995 RingCT/type: yes/0
Extra: 019402fcbb84ad7801d93e7f9178cbcf277051a2afe8d1b40cd1aa8e6fc972863d02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2a5a0555736eb63b028f266d3a4aaa9ca0d3db0d2bb976cd743d442a9f144f4d 0.600000000000 1380670 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": 922974, "vin": [ { "gen": { "height": 922964 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2a5a0555736eb63b028f266d3a4aaa9ca0d3db0d2bb976cd743d442a9f144f4d" } } ], "extra": [ 1, 148, 2, 252, 187, 132, 173, 120, 1, 217, 62, 127, 145, 120, 203, 207, 39, 112, 81, 162, 175, 232, 209, 180, 12, 209, 170, 142, 111, 201, 114, 134, 61, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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