Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7fde21826ba61af6799c2dfd42dc54c2fc0ab64e9a14d8fb333affc97af950f3

Tx prefix hash: 0e03455e477bf36312b786eb17e3ba20fe78912a4372563bacd9fd722fd7f9e1
Tx public key: 425a6c69e15ac68ef68bb7514fd291d4494a7cee77411f0035568187d5ef5c61
Timestamp: 1709201683 Timestamp [UCT]: 2024-02-29 10:14:43 Age [y:d:h:m:s]: 01:032:04:11:01
Block: 968035 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 283993 RingCT/type: yes/0
Extra: 01425a6c69e15ac68ef68bb7514fd291d4494a7cee77411f0035568187d5ef5c610211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 43fa6a962e9d8a2666c395b9fad21899db2fb46dcb00a08b1bdeaa815a7dcf29 0.600000000000 1427832 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": 968045, "vin": [ { "gen": { "height": 968035 } } ], "vout": [ { "amount": 600000000, "target": { "key": "43fa6a962e9d8a2666c395b9fad21899db2fb46dcb00a08b1bdeaa815a7dcf29" } } ], "extra": [ 1, 66, 90, 108, 105, 225, 90, 198, 142, 246, 139, 183, 81, 79, 210, 145, 212, 73, 74, 124, 238, 119, 65, 31, 0, 53, 86, 129, 135, 213, 239, 92, 97, 2, 17, 0, 0, 0, 1, 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