Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ad7ea58cea3f91219f50ff7c11265fff70a701617bc8df591f3ac3aa5b9342c

Tx prefix hash: 62ff50e6c81e5bcac6fb75e727d90d91d23d5068e638f881050463272a3dbf85
Tx public key: 4b1eb6b7f18007fd7c35115244800e81b09361febd1ddfdcfb273f8fc528b4b1
Timestamp: 1706317289 Timestamp [UCT]: 2024-01-27 01:01:29 Age [y:d:h:m:s]: 01:109:13:15:40
Block: 944091 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 339420 RingCT/type: yes/0
Extra: 014b1eb6b7f18007fd7c35115244800e81b09361febd1ddfdcfb273f8fc528b4b102110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e20bb0acea53350f67934490561ba03921c0e750cf0fd64e87d64fd1cab1b4fb 0.600000000000 1402317 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": 944101, "vin": [ { "gen": { "height": 944091 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e20bb0acea53350f67934490561ba03921c0e750cf0fd64e87d64fd1cab1b4fb" } } ], "extra": [ 1, 75, 30, 182, 183, 241, 128, 7, 253, 124, 53, 17, 82, 68, 128, 14, 129, 176, 147, 97, 254, 189, 29, 223, 220, 251, 39, 63, 143, 197, 40, 180, 177, 2, 17, 0, 0, 0, 4, 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