Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 907c265237134e33568f219971ad0fdc7f2f39eb67a3b6a651064e7f6e5a398c

Tx prefix hash: ca1fd2d676f211d2e19f19aa9cc6ef5f9475e354c263ed1d1ef79850801e7d11
Tx public key: 977919e970c9bf9a636251f655cb338830b18b738453409fb8cbbab7f960b673
Timestamp: 1719343915 Timestamp [UCT]: 2024-06-25 19:31:55 Age [y:d:h:m:s]: 00:324:15:54:50
Block: 1052107 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 232023 RingCT/type: yes/0
Extra: 01977919e970c9bf9a636251f655cb338830b18b738453409fb8cbbab7f960b6730211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 21ccc37e37e3860d7b735be951d12f36e49d60c3fa5fd23bd3b3c31a7024920f 0.600000000000 1522428 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": 1052117, "vin": [ { "gen": { "height": 1052107 } } ], "vout": [ { "amount": 600000000, "target": { "key": "21ccc37e37e3860d7b735be951d12f36e49d60c3fa5fd23bd3b3c31a7024920f" } } ], "extra": [ 1, 151, 121, 25, 233, 112, 201, 191, 154, 99, 98, 81, 246, 85, 203, 51, 136, 48, 177, 139, 115, 132, 83, 64, 159, 184, 203, 186, 183, 249, 96, 182, 115, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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