Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 17c4d21765074b38cc66f13a6be0f7edf0fa9c5b2e09db8208ff5746a60ca32f

Tx prefix hash: 8218dfcbf60a7936d1b8c2ab90dfb24a2a09ea4809f2f2c53dd48f91c91bf0d1
Tx public key: 50631cae9722803b6b6ad6e06bdb37a746084a4c7b2586102ad51833242b44bf
Timestamp: 1704051935 Timestamp [UCT]: 2023-12-31 19:45:35 Age [y:d:h:m:s]: 01:104:07:41:08
Block: 925329 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 335690 RingCT/type: yes/0
Extra: 0150631cae9722803b6b6ad6e06bdb37a746084a4c7b2586102ad51833242b44bf02110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9c864d0077c6c568eb87d872318e5e4aadb6815c5356aaf0eac532de8efbd69a 0.600000000000 1383091 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": 925339, "vin": [ { "gen": { "height": 925329 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9c864d0077c6c568eb87d872318e5e4aadb6815c5356aaf0eac532de8efbd69a" } } ], "extra": [ 1, 80, 99, 28, 174, 151, 34, 128, 59, 107, 106, 214, 224, 107, 219, 55, 167, 70, 8, 74, 76, 123, 37, 134, 16, 42, 213, 24, 51, 36, 43, 68, 191, 2, 17, 0, 0, 0, 5, 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