Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fdcf3fa9a714c9669bf3da2193bdc6de3218c1ef955f63d928941f05a1423508

Tx prefix hash: cd9a65068a21d96ba0f02693f3bfa8c6d0e0e0da1bb60c4064dff73e81e30938
Tx public key: 136bcd1db77e1eae7dee3abcb697b59ccada8baa69bbd44b93adcc527bf9d431
Timestamp: 1707649296 Timestamp [UCT]: 2024-02-11 11:01:36 Age [y:d:h:m:s]: 01:058:05:38:02
Block: 955155 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 302667 RingCT/type: yes/0
Extra: 01136bcd1db77e1eae7dee3abcb697b59ccada8baa69bbd44b93adcc527bf9d43102110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4a77b3765a36a04322b1d502c51073d36601993c4b6aa05d238c80c408f69401 0.600000000000 1414441 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": 955165, "vin": [ { "gen": { "height": 955155 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a77b3765a36a04322b1d502c51073d36601993c4b6aa05d238c80c408f69401" } } ], "extra": [ 1, 19, 107, 205, 29, 183, 126, 30, 174, 125, 238, 58, 188, 182, 151, 181, 156, 202, 218, 139, 170, 105, 187, 212, 75, 147, 173, 204, 82, 123, 249, 212, 49, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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