Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 027bd54768c233f91f18117d5124b08829861e97b8833a595a98be6d65a35cab

Tx prefix hash: 1884acb0c276b9e774ec4ce698c60ca5dd10ba5ef84df2eab49f82d94dad9a31
Tx public key: 392c55995d0e5772016e185f6bff6cd5b3d03c7b560ee793a1e6d4cef0da4212
Timestamp: 1707748832 Timestamp [UCT]: 2024-02-12 14:40:32 Age [y:d:h:m:s]: 01:006:08:36:35
Block: 955976 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 265541 RingCT/type: yes/0
Extra: 01392c55995d0e5772016e185f6bff6cd5b3d03c7b560ee793a1e6d4cef0da421202110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8e7d85ee7c7c59e320a6b34f13d0254ae652a9c236b260f740d6642fd5ff3776 0.600000000000 1415278 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": 955986, "vin": [ { "gen": { "height": 955976 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8e7d85ee7c7c59e320a6b34f13d0254ae652a9c236b260f740d6642fd5ff3776" } } ], "extra": [ 1, 57, 44, 85, 153, 93, 14, 87, 114, 1, 110, 24, 95, 107, 255, 108, 213, 179, 208, 60, 123, 86, 14, 231, 147, 161, 230, 212, 206, 240, 218, 66, 18, 2, 17, 0, 0, 0, 5, 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